Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addresses #131. Added check to see if TTY is available. #135

Merged
merged 1 commit into from
Feb 27, 2020

Conversation

joeparsons
Copy link
Contributor

Not sure if this is the kind of fix you had mind for #131 or not, @mglaman, but I copied the Tty class from consolidation/site-process referenced by @danepowell in #131 (comment)

@joeparsons joeparsons requested a review from mglaman February 14, 2020 21:05
@mglaman
Copy link
Owner

mglaman commented Feb 14, 2020

Looks great to me, quick eyeball on mobile. Will come back and merge probably on Sunday

@lpeabody
Copy link

I almost made this exact same PR earlier this afternoon... The irony is this is fixed in symfony/process:^4.1.

@heddn
Copy link

heddn commented Feb 21, 2020

Bump, ran into this recently. I'd rather not pin on an older version.

@heddn
Copy link

heddn commented Feb 21, 2020

@heddn
Copy link

heddn commented Feb 21, 2020

Alternatively, as the prefered install seems to be via phar, just change the composer dependencies to:

"symfony/process": "^4.1"

@lpeabody
Copy link

lpeabody commented Feb 24, 2020

@heddn I don't think that works with Drupal projects though since drupal/core requires symfony/process as ~3.4.0.

EDIT: Right, you said phar, nevermind about the above then if you're using a phar :) For those who aren't using a phar though... it's tough luck until this is merged.

Copy link
Owner

@mglaman mglaman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@mglaman mglaman merged commit 3ec4b60 into mglaman:master Feb 27, 2020
@heddn
Copy link

heddn commented Mar 5, 2020

Could we tag a new release so this gets picked up by my CI?

@hugovk
Copy link

hugovk commented Mar 16, 2020

Yes please for a release!

We'd like to use https://www.drupal.org/project/upgrade_status, but it needs 0.12 of phpstan/phpstan-deprecation-rules, but we use BLT which pins drupal-check <1.1.0 (acquia/blt#4001) and 0.11 of phpstan/phpstan-deprecation-rules, due to #131.

By the way, can #131 be closed now this is merged?

Thank you!

@mglaman
Copy link
Owner

mglaman commented Mar 21, 2020

I kept the issue open to remind me to tag the release 😬

@mglaman
Copy link
Owner

mglaman commented Mar 21, 2020

1.1.1 is out :) thanks for all of the patience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants